* The action will be looked up in action groups that are found among
* the widgets ancestors. Most commonly, these will be the actions with
* the “win.” or “app.” prefix that are associated with the #GtkApplicationWindow
- * or "GtkApplication, but other action groups that are added with
+ * or #GtkApplication, but other action groups that are added with
* gtk_widget_insert_action_group() will be consulted as well.
*
* Since: 3.4
* defines a #GtkShortcutsWindow with ID "help_overlay" then GtkApplication
* associates an instance of this shortcuts window with each
* #GtkApplicationWindow and sets up keyboard accelerators (Control-F1
- * and Control-?) to open it. To create an menu item that displays the
- * shortcuts window associate the item with the action win.show-help-overlay.
+ * and Control-?) to open it. To create a menu item that displays the
+ * shortcuts window, associate the item with the action win.show-help-overlay.
*
* ## A simple application ## {#gtkapplication}
*
* types of actions that may be blocked are specified by the @flags
* parameter. When the application completes the operation it should
* call gtk_application_uninhibit() to remove the inhibitor. Note that
- * an application can have multiple inhibitors, and all of the must
+ * an application can have multiple inhibitors, and all of them must
* be individually removed. Inhibitors are also cleared when the
* application exits.
*
* @title: GtkApplicationWindow
* @short_description: GtkWindow subclass with GtkApplication support
*
- * GtkApplicationWindow is a #GtkWindow subclass that offers some
+ * #GtkApplicationWindow is a #GtkWindow subclass that offers some
* extra functionality for better integration with #GtkApplication
* features. Notably, it can handle both the application menu as well
* as the menubar. See gtk_application_set_app_menu() and
* prefix. Actions must be addressed with the prefixed name when
* referring to them from a #GMenuModel.
*
- * Note that widgets that are placed inside a GtkApplicationWindow
+ * Note that widgets that are placed inside a #GtkApplicationWindow
* can also activate these actions, if they implement the
- * GtkActionable interface.
+ * #GtkActionable interface.
*
* As with #GtkApplication, the GDK lock will be acquired when
* processing actions arriving from other processes and should therefore
*
* Normally, the connection between the application and the window
* will remain until the window is destroyed, but you can explicitly
- * remove it by setting the ::application property to %NULL.
+ * remove it by setting the :application property to %NULL.
*
* Since: 3.0
*/